Repository navigation
ci: fix Release Please and automate standalone release assets - #23
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release management
Release Please now uses the root package’s existing
v0.1.0tag as its baseline. The Node strategy keeps the package, lockfile, manifest, and changelog in sync. Conventional Commits populate the existing Added, Changed, Fixed, Security, and Maintenance headings. Ordinary documentation, chore, CI, build, test, and style commits do not trigger a release.The workflow retains
skip-labelingand restores the pending marker that the pinned action uses to recognize its own release PR after merge. The pinned changelog generator has no option to include commit authors in individual entries.Standalone HTML
When Release Please creates a release, the same workflow checks out its exact tag, builds on Node.js 22.23.5, and uses the tagged commit time for the embedded build timestamp. It checks the package version and nonempty HTML, uploads only
OWASP-DecodeBox-Standalone-vX.Y.Z.html, sets the release title, and verifies the uploaded filename and SHA-256 digest. Release Please retains ownership of the release notes.For recovery, run Release Please from
mainwith an existing stable tag inrelease_tag. This bypasses release creation and rebuilds the matching asset. The originalv0.1.0release is protected.Verification
mainproduced no release candidate. A simulated future fix comparedv0.1.0...v0.1.1and excluded all ten historical fixes listed in chore(release): OWASP DecodeBox v0.1.1 #19.PR #19 still proposes the obsolete bump under the configuration on
main. The first run after this change lands can reevaluate it.